github: remove obsolete secret setting
#124
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Long replaced by `client_secret`, along with slightly janky (because it auto-rewrites Sopel's config file, erasing comments) auto-migration code to move the old `secret` value to the new place where it belongs. Was meant to be removed in 0.3.0, but we went through the whole 0.4.x series with this still present.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Long replaced by
client_secret, along with slightly janky (because it auto-rewrites Sopel's config file, erasing comments) auto-migration code to move the oldsecretvalue to the new place where it belongs.Was meant to be removed in 0.3.0, but we went through the whole 0.4.x series with this still present.